home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
btrieve
/
bj516b.exe
/
BUGS.516
< prev
next >
Wrap
Text File
|
1993-04-12
|
4KB
|
86 lines
40. NLM Btrieve: BTRIEVE.NLM, version 5.16
Fixes the following bug: under certain rare conditions, Btrieve
fails to recover a file's preimage after an error that would have
returned a status 2. A status 15 is returned instead, and later
attempts to open the file may fail with a status 14. This patch
ensures that the original status 2 is returned and that the file's
preimage is rolled-back.
41. NLM Btrieve: BTRIEVE.NLM, version 5.16
When using BREQUEST version 6.0 or higher, a user with only Read
and File Scan rights in a directory is not allowed to open
a Btrieve file in Read-Only mode; instead Btrieve incorrectly
returns an error, status 94, Permission Error. This patch fixes
the bug.
42. NLM Btrieve: BTRIEVE.NLM, version 5.16
If, having started a transaction, the first operation is an insert
and the record has a duplicate key and the logging is active for that
file Btrieve will erroneously make a second BEGIN_TRANSACTION entry
in the log file. This second entry causes a status 37 when rolling
forward the file. The patch prevents Btrieve from logging twice
the same BEGIN_TRANSACTION.
43. NLM Btrieve: BTRIEVE.NLM, version 5.16
If you have a file with key and both the duplicates and null keys are
allowed, a GET DIRECT (op.23) on a record with null key could give
different status codes (st.82 or st.44) depending on whether the key is
a permanent or a supplemental key. This patch ensures that always the
proper status code (44) will be returned on a GET DIRECT like that.
44. NLM Btrieve: BTRIEVE.NLM, version 5.15
If the machine is turned off or rebooted between the time a Btrieve
file has marked as having a pre-image file and the time the pre-image
file is created, the file cannot be opened. Btrieve returns status 14.
This patch fixes the problem caused by a timing window, and it ensures
that the file can be opened.
45. NLM Btrieve: BTRIEVE.NLM, version 5.15
Doing a Delete (op. 4) followed by a Get Next (op. 6) on a key-only
file with duplicated key values where the key consists of more than
one segment, the given status or record was not the proper one.
This patch ensures that both the status and the record are correct.
46. NLM Btrieve: BTRIEVE.NLM, version 5.16
Given a file with corruption on the variable pages (specifically
corrupt page number fields), Btrieve would return a status 2,
thwarting efforts to recover the file be using Step Next (or
Step Previous) to retrieve undamaged records. This patch causes
Btrieve to return the correct status code, 54, which in addition
to returning the first part of the record, also advances the
position block farther into the file so that subsequent, undamaged
records can be retrieved.
47. NLM Btrieve: BTRIEVE.NLM, version 5.16
When Stepping through a file with corrupted pages (specifically
corrupt page number fields), Btrieve would sometimes have trouble
returning a record from the first good page read after a series of
bad pages. This patch fixes the problem.
48. NLM Btrieve: BTRIEVE.NLM, version 5.16
Doing Op.11s (GET_LE) on a key-only file or on a file with supplemental
key where the duplicates are allowed, Btrieve does not always set the
position properly. This patch ensures the correct positioning at any
case.
49. NLM Btrieve: BTRIEVE.NLM, version 5.16
After an application does a Get Less Than or a Get Less Than
or Equal (opcodes 10 and 11) with an empty file and receives
a status 9 (End of File) error, if it does a Get Position,
garbage is returned in the data buffer, instead of a record
address and the status code is set to 0, indicating no error.
This patch ensures that the status code is set to 8, Invalid
Positioning.